home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000313_news@columbia.edu_Wed Sep 6 09:04:17 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA17439
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 7 Sep 1995 08:30:12 -0400
Received: by apakabar.cc.columbia.edu id AA23422
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 7 Sep 1995 08:30:11 -0400
Path: news.columbia.edu!panix!news.mathworks.com!tank.news.pipex.net!pipex!in2.uu.net!EU.net!howland.reston.ans.net!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-KERMIT 3.14 hanging on idle TCP/IP connection?
Message-Id: <1995Sep6.150417.60686@cc.usu.edu>
Date: 6 Sep 95 15:04:17 MDT
References: <42d2u9$edt@apakabar.cc.columbia.edu> <42kk5c$afd@dartvax.dartmouth.edu>
Organization: Utah State University
Lines: 32
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <42kk5c$afd@dartvax.dartmouth.edu>, randy.witlicki@pop.valley.net (Randy Witlicki) writes:
> I have another data point to add and perhaps confuse things:
>
> I recently helped a library convert from a DOS based library
> automation package to a UNIX based system (Innopac from
> Innovative Interfaces). Most of the PCs are of the diskless
> 286 and 386 variety on a Novell Netware network. The
> protocol stack was monolithic IPX/NETX which I updated
> to current NETX with the odipkt shim so kermit could talk TCP/IP.
> The existing frame type was 802.3 so I added Ethernet_II to
> the Net.CFG files. (to be updated to Ethernet_II only at some
> future date). This is a single segment network with
> bridges, routers, or other outside connections.
> The Unix box is a Dec Alpha 3000.
> The PCs have DANET (Direct Access - Network) as their
> menu front end.
>
> So, to finally get to the problem: After about 10 minutes of
> sitting idle, the Kermit TCP/IP connection to the UNIX box
> times out and the PC drops back to the menu program - it
> doesn't hang, no reboot needed, it just drops the connection
> after about 10 minutes....
----------
Hmmmm, as they say. I have an idea, one needing a little assistance
from your side. The idea is the other end is using one method of TCP
session keepalives and Kermit is expecting another. The assistance is
to record packets around the ten minute mark and send me the ASCII packet
dumps. That takes a packet monitor, and ones doing nifty recording/dumps are
not free.
Anyone else able to duplicate this experimental setup?
Thanks,
Joe D.